Skip to content

chore(main): release 9.15.0#394

Open
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main
Open

chore(main): release 9.15.0#394
github-actions[bot] wants to merge 1 commit intomainfrom
release-please--branches--main

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jan 2, 2026

🤖 I have created a release beep boop

9.15.0 (2026-02-04)

Features

Bug Fixes

  • Add context manager for clearer, safer locks (#396) (beca0fa)
  • Address potential race condition in FeatureStore update_availability (#391) (31cf487)
  • Allow modifying fdv2 data source options independent of main config (#403) (d78079e)
  • Prevent immediate polling on recoverable error (#399) (da565a2)
  • Redis store is considered initialized when $inited key is written (e99a27d)
  • Stop FeatureStoreClientWrapper poller on close (#397) (468afdf)
  • Update DataSystemConfig to accept list of synchronizers (#404) (c73ad14)
  • Update reason documentation with inExperiment value (#401) (cbfc3dd)
  • Update Redis to write missing $inited key (e99a27d)

This PR was generated with Release Please. See documentation.


Note

Low Risk
Release-only metadata/documentation and version bumps; no functional code changes in this PR beyond updating the reported SDK version string.

Overview
Cuts the 9.15.0 release by bumping version references across the repo (.release-please-manifest.json, pyproject.toml, ldclient/version.py) and updating PROVENANCE.md to reference the new release.

Adds a CHANGELOG.md entry for 9.15.0, documenting the shipped feature changes (including dropping Python 3.9 support and requiring a selector for ChangeSet) and several bug fixes (locking, feature store availability race, polling behavior, Redis $inited, FDv2 options, and synchronizer configuration).

Written by Cursor Bugbot for commit 9306346. This will update automatically on new commits. Configure here.

@github-actions github-actions bot requested a review from a team as a code owner January 2, 2026 19:13
@github-actions github-actions bot force-pushed the release-please--branches--main branch 5 times, most recently from ba17918 to 90a4a78 Compare January 7, 2026 17:07
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 90a4a78 to 204b5d6 Compare January 13, 2026 17:31
@github-actions github-actions bot force-pushed the release-please--branches--main branch 2 times, most recently from 9ebed09 to 87461a3 Compare January 21, 2026 14:45
@github-actions github-actions bot force-pushed the release-please--branches--main branch 4 times, most recently from b74f540 to 4393169 Compare February 4, 2026 16:27
@github-actions github-actions bot force-pushed the release-please--branches--main branch from 4393169 to 9306346 Compare February 4, 2026 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants